Enterprise Portal provides an extensive automation framework to meet the needs of different organizations. This framework is based on two basic concepts that can be combined as required: Rules and Actions.

Rules and Actions are managed via the separate modules of the Enterprise Portal:

  • SIM Rules (i.e. Rules that define event conditions related to SIM Cards) are created and managed in the SIM Rules section under the SIM Cards tab.
  • Pool Rules (i.e. Rules that define event conditions related to SIM Pools) are created and managed in the Pool Rules section under the SIM Pools tab.
  • Actions are created and managed in the Actions section, which can be located both under the SIM Cards and SIM Pools tab.
    Note that selecting the Actions tab under SIM Pools will redirect you to the Actions tab under the SIM Cards tab.

Rules

Rules define conditions, which when fulfilled, automatically trigger an Action.

These conditions can be based on usage of a SIM Card or SIM Pools, or changes to the SIM Cards properties.

Examples

Condition 1 - Usage: Data usage of a SIM Card in a specific Country has reached a threshold set in the Rule definition.

Condition 2 - Properties: Detection of a change to the IMEI number of a device to which the SIM Card is assigned.

Actions

The second component of the automation framework is Actions, which represent system processes activated when the conditions in the related Rule(s) are met. Actions can be assigned to both SIM and Pool Rules.

Usage Example

The following scenario represents a municipality that has implemented smart metering devices for the management of public parking spaces. The CMP's framework of automated Rules and Actions provides this municipality with the tools needed for the proficient management of each SIM and Device.

  • Security: Access Points to a network, such as IoT devices, are targets for malicious infiltration. Left undetected, attackers can hijack a device's software to control a SIM's data connection for their own usage, and potentially gain further access to a private network. The municipality can draw from usage history records of each parking space to determine individual thresholds for the rules Data Sessions Count - 24hrs and Data Usage Total - 24hrs. When combined with the action Deactivate SIM and Email Notification, the municipality will detect suspicious data activity and deactivate a potentially compromised device before major damage can occur.
  • Service: The amount of time required to detect a non-functioning device is a critical measurement. No matter the location or application, IoT devices or their SIM cards can experience disruptions to their normal function that will require the attention of a field technician.  For a municipality, Downtime for a smart meter equates to lost revenue and poor quality of service to its residents. By applying the rule Not Connected - 24hrs or Not Connected - Billing Cycle with the action Email Notification, the service department will be notified of a faulty meter, and a field technician can be dispatched within hours.